Venus Taneja
← All work
FLIPKART · BIG BILLION DAYS

Big Billion Days 2017

How a Hindi campaign line became a text-free visual language, a monolithic homepage became a modular system, and one storefront split into category frameworks for India’s largest sale.

RoleLead Designer, Event Experience
Team4 designers, 2 copywriters
PlatformsAndroid, iOS, Desktop, Mobile Web
PartnersProduct, Marketing, Category teams
CONTEXT

Flipkart’s flagship sale, with a target to double it

Big Billion Days (BBD) is Flipkart’s flagship commercial event, a fast, high-volume shopping festival comparable to Black Friday. By 2016 it had grown to $500M in GMV. For 2017 the goal was to double total sales and take clear market leadership in our three biggest categories: Mobiles, Fashion and Large Appliances.

As Lead Designer for the Event Experience, I owned the end-to-end user journey across the native apps, desktop and mobile web. I led a pod of four designers and two copywriters, and drove alignment across product, marketing and the commercial category teams.

2016 baseline
$500M
GMV from the previous edition
2017 goal
2×
Double total sales and lead in key categories
Surface
4
Android, iOS, Desktop and Mobile Web, designed as one journey
CHALLENGE

At this scale, growth creates fragmentation and cognitive load

We identified three structural bottlenecks that needed a systematic design response rather than more screens.

01

Turn a copy-led campaign into a universal visual language

The campaign rested on the Hindi tagline “Ab Mehengaai Giregi” (Prices are about to fall). It resonated culturally but depended on reading. In a multilingual, multi-demographic market, text-dependence costs conversion. We needed to turn an abstract economic idea into a visual cue anyone could recognize in under a second.

02

Stop the UI fragmenting across business units

Separate business units run each category, so Mobiles and Fashion historically shipped their own look during big sales. We needed one design system that could scale across hundreds of pages without review bottlenecks or extra engineering overhead.

03

Replace the one-size-fits-all storefront

A single static homepage could not carry the growth target. A premium smartphone buyer needs spec comparisons and EMI options. An apparel shopper needs immersive, high-fidelity visuals. The experience had to adapt to intent while keeping the brand coherent.

STRATEGY & EXECUTION

Three tracks, one for each bottleneck

I split execution into a visual framework, a component-driven homepage and category-specific UX frameworks, so each team knew which problem it was solving.

A

Translating the cultural metaphor into UI

We personified Mehengaai (inflation, high prices) as a playful antagonist inside the interface. Banners stopped being static ads. The components themselves crushed, cracked and dropped high prices.

Color strategy
A high-contrast, celebratory palette that kept accessible contrast ratios while signaling urgency and a festive, premium feel.
Language-agnostic cues
Custom price-drop icons and micro-interactions that show value being subtracted, cutting across literacy and language barriers.
The system that scaled. A festival identity strict enough for dozens of teams, flexible enough for nine days of daily change.
B

A modular homepage architecture

To personalize at the scale of 214 million visitors, we retired the monolithic landing page. In its place we built a layout-agnostic slotting system of dynamic structural widgets.

Every module was bound to one responsive grid and one set of spacing tokens. However the algorithm assembled the page for a given profile, the layout stayed balanced and high-fidelity.

FixedEvent hero, grid, spacing tokens, type scale
FlexibleWhich widgets fill each slot, and in what order
SafeguardFallback rules keep the page balanced for any combination of data
C

Category-specific information architecture

We set aside generic e-commerce layouts. Using user research and past sale analytics, we mapped a distinct buying mindset per category and rebuilt each landing page around it. Each list below is the order of visual priority.

Mindset · Evaluate
Electronics & Mobiles
  • 1Tabular spec comparison
  • 2Transparent device exchange value
  • 3Absolute discount (₹ off) instead of percentages
Lowers friction on high-ticket decisions.
Mindset · Explore
Fashion & Lifestyle
  • 1Larger image aspect ratios, high-fidelity product shots
  • 2Lifestyle lookbooks
  • 3Minimal text density
Encourages exploratory browsing.
Mindset · Reassure
Large Appliances
  • 1Warranty details
  • 2Delivery scheduling widgets
  • 3Affordability options such as No-cost EMI
Puts reassurance at the top of the hierarchy.
OPERATIONAL LEADERSHIP

A design system is only as good as its execution

To deploy across dozens of cross-functional category pods, the system needed governance as much as components.

The playbook
BBD Design Guidelines
I co-authored a layout manual covering asset specs, typographic scale, image shoot direction and interaction specs.
Autonomous enablement
−50%
Shared early as a single source of truth, the playbook let category teams build their verticals on their own. Cross-team alignment and review cycles fell by more than half.
Cross-functional alignment
Daily triage loops
With Product and Engineering leadership, to ship complex responsive layouts and interactions precisely, without adding latency under peak load.
MEASURED IMPACT

The 2017 edition broke every platform record

Business metrics
70%Market share in India across Fashion, Mobiles and Appliances
12.1MUnits sold during the event
+47%Year-over-year growth in transaction volume
110%Average selling price against target, driven by clearer high-value category frameworks
Design system legacy

The template for every major event that followed

The BBD 2017 framework became the foundation for Flipkart’s major event systems across several later editions. It changed how the team worked.

Reactive asset creation → Proactive, componentized system
TAKEAWAYS

What I carry into every project since

01

Substance over trends

Localized UX depends on real cultural resonance. Turning a colloquial idiom into intuitive, text-free patterns was worth far more than borrowing generic Western e-commerce conventions.

02

Scale requires ecosystem thinking

For hundreds of millions of users and many independent teams, static screens do not scale. You design rules, constraints and components that let others build coherently.

03

Design the logic, not just the UI

Personalization is a design problem. An algorithmic storefront needs fallback rules, modular layout constraints and visual balance safeguards so the interface stays clean for any permutation of data.

NEXT CASE STUDY Pay history setup, from 10 days to 30 minutes
→